… view

The provider is released independently of core and may run against an older
Airflow that predates the AccessView.IMPORT_ERRORS_ALL member (added in 3.4.0).
Referencing it directly in the resource map raised AttributeError at import
time under the provider compatibility matrix. Resolve the member through a
common.compat shim and map it only when the running core defines it.

…lease

The IMPORT_ERRORS_ALL access-view shim is added to the common.compat provider in
this same PR, so fab and keycloak require the next common.compat release. The
selective-check common-compat guard enforces the '# use next version' marker on
those dependents; add it so the build-info check passes and the compatibility
tests run.

The same relative_fileloc can exist in more than one bundle, so matching only on
the filename treated an import error whose file has no Dag in its own bundle as
registered when another bundle happened to define a Dag for the same path. Join
the has-any-Dag subquery on both filename and bundle_name so unregistered-file
import errors are detected per bundle.

The shim module was added without a matching test, which the provider
project-structure check flags. Cover both branches: it resolves to the enum
member on a core that defines it, and to None on an older core that does not.

The list endpoint joins the has-any-Dag subquery twice; only the first was
scoped to the bundle. Since the subquery now yields one row per (file, bundle),
the remaining filename-only join could duplicate an error across bundles and
mis-detect registration. Join on bundle_name there too, add a regression test
for a file registered only in another bundle, and update the existing bundle
-join test, whose old expectation encoded the pre-fix cross-bundle leak.

The provider compatibility matrix runs this test against older cores that
predate AccessView.IMPORT_ERRORS_ALL (or lack api_fastapi entirely), where
referencing the member directly raised AttributeError. Compare the shim against
whatever the running core exposes (the member, or None) so it holds everywhere.

…point

The has-any-Dag lookup in get_import_error is scoped per bundle. Without
that scoping a same-named file registered in a different bundle resolved
as a Dag match, so the endpoint returned the raw stacktrace on the
strength of an unrelated bundle's read permission instead of gating on
IMPORT_ERRORS_ALL. The list endpoint already had this coverage.

The team_name argument no longer forces a hard break — auth managers that
predate it keep working with a deprecation warning — so it is a feature rather
than a significant/breaking change. Replace the significant newsfragment with a
single feature note that states when team_name became available (Airflow 3.4.0)
and which bundled auth managers support it, and move the implementation detail
(the authorize_view fallback, the deprecation, how to make a manager team-aware)
into the auth manager documentation where implementers will look for it.